Printer system, printer, and image registration method

ABSTRACT

A printer, image registration method, and printer system improve image data processing efficiency by tracking and storing the identical image data that is registered and stored in a printer. The image registration device has a graphics register for registering images in a printer. The graphics register sends the image data to be registered to the printer, receives an identification number from the printer, and records and stores a registered image data information file linking the image data sent to the printer with the printer identification number.

Priority is claimed from Japanese Patent Application 2005-118964 filedon Apr. 15, 2005 and Japanese Patent Application 2005-174358 filed onJul. 14, 2005, which are hereby incorporated by reference in theirentirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a printer in which images can beregistered and stored, to an image registration device for registeringimages in the printer, to an efficient printer system composed of thisprinter and image registration device, and to an image registrationmethod.

2. Description of Related Art

Some printers that are used in POS systems enable the user to storeimage data in the printer. Such printers typically have internalnonvolatile storage such as NVRAM in which image data representing thestore logo, coupons, or other information is stored. The printer thenprints the image data on roll paper, for example, based on commands fromthe host computer to issue a sales receipt. Compared with a text-onlyreceipt, this enables the store to print more attractive receipts,creating a more favorable impression on the customer.

This system also eliminates the need for the host computer to send theimage data to the printer each time a receipt is printed because theimage data resides in the printer. Image data can thus be printedfrequently even when the communication rate between the host and printeris slow and the system is thus not well-suited to transferring largeimages.

A key code or identification (ID) code that uniquely identifies eachimage is assigned to each image data file stored in the printer. Theimage data is managed in the printer using the key code assigned to eachimage. When the printer receives a key code or a print commandassociated with a particular key code from the host computer at apredetermined timing, the printer prints to roll paper the image datacorresponding to the received key code or the image associated with thepredefined command. The host computer can thus simply send theappropriate key code or print command associated with a particular keycode to cause the printer to print a particular image.

A problem with this conventional arrangement is that it is difficult forthe user to know what image corresponds to a particular key code. Inorder for the user to edit image data stored in the printer, he or shemust enter a key code and print a hard copy preview of the correspondingimage, or print a test page of key codes and corresponding images inorder to select and edit the desired image.

Furthermore, in order to preview the images on the display of the hostcomputer, the image data must be acquired from the printer.

If the printer is connected through a serial interface or othersimilarly slow interface, time will be wasted waiting for the image datato travel between the printer and host computer, thus reducing dataprocessing efficiency.

To solve these problems, an object of the present invention is toprovide a printer in which images can be stored while enabling the userto efficiently process the stored image data using an image registrationdevice, an efficient printer system comprising these devices, and animage registration method for registering images in the printer.

SUMMARY OF THE INVENTION

To achieve this object, a printer system according to a first embodimentof the invention is a printer system comprising an image registrationdevice capable of communicating with a printer, wherein: the imageregistration device sends image data and an image data registrationcommand to the printer; the printer includes a data communication unitfor receiving commands and image data sent from the image registrationdevice, and an image registration unit for registering the receivedimage data in a designated storage area; the data communication unitsends a printer identification number to the image registration devicewhen image data is registered; and the image registration device recordsthe image data and the received printer serial number in a registrationlog file.

A printer system according to a second embodiment of the invention isthe printer system according to the first embodiment of the inventionwherein the image registration device generates a key code identifyingthe image data, sends the key code paired with the image data to theprinter, and records the path describing the storage location of thesource file of the image data linked to the key code in the registrationlog file.

A printer system according to a third embodiment of the invention is theprinter system according to the second embodiment of the inventionwherein the image registration device applies an image conversionprocess to the source image file to generate and send the image data tothe printer, and records the path describing the storage location of thesource image file linked to the parameters of the applied imageconversion process in the registration log file.

A printer system according to a fourth embodiment of the invention isthe printer system according to the third embodiment of the inventionwherein the image registration device sends a delete command denotingthe image data to be deleted to the printer in order to delete imagedata from the printer; the image registration unit of the printerdeletes the image data specified in the delete command and returns theprinter identification number to the image registration device; and theimage registration device accesses the registration log filecorresponding to the printer identification number, deleting the recordof the image data corresponding to the image data deleted in theprinter.

A printer system according to a fifth embododiment of the invention isthe printer system according to any of the first to fourth embodimentsof the invention wherein the image registration device accesses theregistration log file to present a preview of the corresponding imagedata registered in the printer.

A printer system according to a sixth embodiment of the invention is theprinter system according to any of the first to fifth embodiments of theinvention wherein the printer additionally includes an identificationnumber overwriting unit for generating a new printer identificationnumber and overwriting the existing printer identification number eachtime a process is run by the image registration unit; the communicationunit of the printer sends the new printer identification number to theimage registration device after processing by the image registrationunit ends; and the image registration device records the new printeridentification number linked to the transmitted image data in theregistration log file.

A printer system according to a seventh embodiment of the invention isthe printer system according to the sixth embodiment of the inventionwherein the image registration device receives the printeridentification number from the printer before sending image data, and ifthere is a registration log file that matches the received printeridentification number, receives a new printer identification number fromthe printer after sending the image data to the printer, and associatesthat image data to the new printer identification number in theregistration log file.

A printer system according to an eighth embodiment of the invention isthe printer system according to the sixth embodiment of the inventionwherein the image registration device receives the printeridentification number from the printer before sending image data, and ifthere is no registration log file associated with the received printeridentification number, receives a new printer identification number fromthe printer after sending the image data to the printer, and generates aregistration log file associating the new printer identification numberwith the sent image data.

A printer system according to a ninth embodiment of the invention is theprinter system according to the sixth embodiment of the inventionwherein the image registration device receives the printeridentification number from the printer before sending a delete commandfor image data registered in the printer, and deletes the image datainformation from the registration log file after sending the deletecommand to the printer if there is a registration log file associatedwith the received printer identification number.

A printer system according to a tenth embodiment of the invention is theprinter system according to the sixth embodiment of the inventionwherein the image registration device receives the printeridentification number from the printer before displaying image dataregistered in the printer, and displays the image data without acquiringthe image data from the printer if there is a registration log fileassociated with the received printer identification number.

A printer system according to an eleventh embodiment of the invention isthe printer system according to the sixth embodiment of the inventionwherein for linked image data in the registration log file, the imageregistration device accesses the registration log file and displays theimage data without acquiring image data from the printer.

A twelfth embodiment of the invention is a printer enabled tocommunicate with an image registration device, the printer comprising: adata communication unit for receiving image data sent from the imageregistration device; and an image registration unit for registering thereceived image data in a designated storage area; wherein the datacommunication unit sends to the image registration device a printeridentification number enabling the image registration device to link theimage data with that of the printer to which the image data was sent.

A printer according to a thirteenth embodiment of the invention is aprinter according to the twelfth embodiment of the invention furthercomprising an identification number rewriting unit for overwriting theprinter identification number with a new printer identification numbereach time a process is executed by the image registration unit; whereinthe data communication unit sends the new printer identification numberto the image registration device each time the identification numberrewriting unit overwrites the printer identification number.

A printer according to a fourteenth embodiment of the invention is aprinter according to the thirteenth embodiment of the invention whereinthe printer identification number is composed of the serial number ofthe printer and a predetermined character string; and the identificationnumber rewriting unit rewrites the printer identification number byoverwriting the predetermined character string.

A fifteenth embodiment of the invention is an image registration methodcomprising steps of: sending image data to be registered to a printer;receiving from the printer a printer identification number; andrecording the transmitted image data and the received printeridentification number in a registration log file.

An image registration method according to a sixteenth embodiment of theinvention is the image registration method according to the fifteenthembodiment of the invention further comprising steps of: generating akey code identifying image data; and additionally registering the pathdescribing the storage location of the source image file of the imagedata linked to the key code in the registration log file.

An image registration method according to a seventeenth embodiment ofthe invention is the image registration method according to thesixteenth embodiment of the invention further comprising steps ofgenerating the image data to be registered by applying an imageconversion process to the source image file; and additionally recordingthe path describing the storage location of the source image file linkedto the parameters of the applied image conversion process in theregistration log file.

An image registration method according to an eighteenth embodiment ofthe invention is the image registration method according to theseventeenth embodiment of the invention further comprising steps ofsending a delete command denoting image data to be deleted to theprinter; receiving a printer identification number from the printer; andidentifying a registration log file associated with the printeridentification number and deleting the record of the image data in theregistration log file corresponding to the deleted image data in theprinter.

An image registration method according to a nineteenth embodiment of theinvention is the image registration method according to any of thefifteenth to eighteenth embodiments of the invention further comprisinga step of accessing the registration log file to present a preview ofimage data registered in the printer.

An image registration method according to a twentieth embodiment of theinvention is the image registration method according to the nineteenthembodiment of the invention wherein the printer identification number isreceived from the printer to identify the registration log file to beaccessed when presenting a preview.

When the image registration device sends image data to be registered tothe printer, the image registration device also receives a printeridentification number (printer ID number) from the printer, and recordsthe transmitted image data with the printer ID number in a registrationlog file. The image registration device can therefore reliably store andretrieve the same image data that was sent to each printer. The user canthus know what images are stored in which printers without having toprint a test image or proof sheet of thumbnail images from each printer.

The image registration device can also apply an image conversion processto the original image file to generate or modify image data sent to theprinter, and can store a path describing where the original image fileis stored, together with the parameters of the image conversion processin the registration log file. The image registration device cantherefore apply the same image conversion process based on the storedparameters to the image file stored in the image registration device andthus present an image data preview without acquiring the image data fromthe printer. The present invention thus also enables the rapidpresentation of an image preview even if the printer and imageregistration device are communicating through a slow data communicationchannel.

In order to delete image data from the printer, the image registrationdevice can simply send a delete command declaring what image data todelete to the printer and receive the printer ID number from theprinter. The image registration device can then use the printer IDnumber to identify the appropriate registration log file and delete thecorresponding record for the deleted image data from the registrationlog. The registration log file maintained in the image registrationdevice is thus always kept up to date so that the registration logalways records what image data is actually stored in the printer, andthe image registration device thus always stores the same image datathat is stored in the printer without actually querying the printer oracquiring the image data from the printer.

The image registration device can also read the registration log file topresent a preview of the image data stored in a particular printer. As aresult, the user can preview the image data stored in a particularprinter without the image registration device actually acquiring theimage data from the printer.

Yet further, the image registration device receives a printer ID numberfrom each printer and uses the printer ID number to identify theregistration log file to be read. As a result, the image registrationdevice can appropriately present a preview of images stored in aparticular printer even when the image registration device stores imagedata corresponding to images stored in a plurality of printers.

Yet further, in response to a command from the image registrationdevice, the printer ID number inside the printer can be overwritten eachtime the image registration unit of the printer operates, and the newprinter ID number can be sent to the image registration device. Theimage registration device then saves the received printer ID number andcorresponding image data in the registration log file. As a result, if adifferent image registration device changes the image data orinformation related to the image data saved in a printer, whether theinformation stored by the image registration device matches theinformation stored in the printer can be easily verified by comparingthe printer ID number stored by the printer with the printer ID numbersrecorded in the registration log file of the image registration device.This prevents a mismatch between the information stored by the printerand the information maintained by the image registration device in theevent image data saved in the printer is mistakenly manipulated.

Other objects and attainments together with a fuller understanding ofthe invention will become apparent and appreciated by referring to thefollowing description and claims taken in conjunction with theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a POS system according to the presentinvention.

FIG. 2 is a control block diagram for a printer and image registrationdevice according to a first embodiment of the invention.

FIG. 3 shows parameters stored by the printer.

FIG. 4 describes the receipt design process.

FIG. 5 is a block diagram of the printer control program.

FIG. 6 shows a sample of a gateway window.

FIG. 7 shows an example of a screen displayed in a window of thegraphics register.

FIG. 8 shows an example of another screen displayed in a window of thegraphics register.

FIG. 9 shows an example of another screen displayed in a window of thegraphics register.

FIG. 10 shows an example of another screen displayed in a window of thegraphics register.

FIG. 11 shows an example of a screen displayed in a window of thereceipt designer.

FIG. 12 shows an example of another screen displayed in a window of thereceipt designer.

FIG. 13 shows an example of another screen displayed in a window of thereceipt designer.

FIG. 14 shows an example of another screen displayed in a window of thereceipt designer.

FIG. 15 shows an example of another screen displayed in a window of thereceipt designer.

FIG. 16 shows an example of another screen displayed in a window of thereceipt designer.

FIG. 17 is a flow chart of a process for registering image data in aprinter according to a first embodiment of the invention.

FIG. 18 is a flow chart of a process for deleting image data in aprinter according to a first embodiment of the invention.

FIG. 19 is a flow chart of a process for previewing image data in aprinter according to a first embodiment of the invention.

FIG. 20 is a control block diagram of a printer and image registrationdevice according to a second embodiment of the invention.

FIG. 21 is a flow chart of a process for registering image data in aprinter according to a second embodiment of the invention.

FIG. 22 is a flow chart of a process for deleting image data in aprinter according to a second embodiment of the invention.

FIG. 23 is a flow chart of a process for acquiring image data key codesfrom the printer and displaying a preview of the image data in a secondembodiment of the invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Preferred embodiments of a printer that can store images internally, animage registration method for registering images in the printer, and aprinter system composed of the printer and image registration deviceaccording to the present invention are described below with reference tothe accompanying figures.

Embodiment 1

A first embodiment of a printer, an image registration device, and aprinter system according to the present invention are described firstbelow.

FIG. 1 is a schematic block diagram of a POS system used by way ofexample as a printer system according to a first embodiment of theinvention, FIG. 2 is a control block diagram of the image registrationdevice and printer, FIG. 3 shows some of the parameters and argumentsstored by the printer, and FIG. 4 shows an example of a receipt designprocess.

As shown in FIG. 1, the printer 50 in this embodiment of the inventionis used in a POS system for printing receipts based on informationrelating to product sales entered by the store or other user. Theprinter 50 prints transaction information print data, which is generatedby the POS application 41 a running on the POS terminal device 40,received from the POS terminal device 40 to roll paper, and thus outputsa receipt. Based on previously stored print settings, the printer 50runs a receipt design process (described in detail below) for addingimage data to the transaction information print data received from thePOS terminal device 40 to print a receipt. The parameters of thisreceipt design process are set by the image registration device 10connected to the printer 50. This image registration device 10 is shownin FIG. 1 as a device separate from the POS terminal device 40, but theimage registration device 10 and the POS terminal device 40 could be thesame device.

The POS terminal device 40 is connected through a wireless or wiredinterface to the printer 50. The POS terminal device 40 acquires inputdata about the products from a keyboard 43 or barcode reader 44. The POSterminal device 40 reads a customer 55 credit card or membership card,for example, by means of a card reader 45 in order to acquire memberinformation or the information needed to complete a credit cardtransaction. The POS terminal device 40 also has a display 42 forpresenting product information generated from the product data sent fromthe POS server 30 in order to display the purchased products and pricesfor the customer 55 to see. These operations are controlled by the POSapplication 41 a running on the POS terminal device 40. The POSapplication 41 a generates the transaction information print data forprinting on a receipt based on the product data sent from the POS server30 and the input data, and sends the transaction information print datathrough the printer driver 41 b to the printer 50.

In addition to a control device (CPU 31), the POS server 30 also hasmemory such as ROM 32 and RAM 33, and processes the information storedin a buffer 39 inside RAM 33 according to a control program stored inROM 32. A product master composed of a product code block 35, productname block 36, price block 37, and inventory block 38 is stored in RAM33. Based on input data sent from the POS terminal device 40, the CPU 31extracts the product code, product name, and product price informationfrom the product master, and generates the product data used forprinting a receipt R and presentation on the display 42.

The printer 50 is a receipt printer composed of a data communicationunit 100 for receiving control commands and transaction informationprint data from the POS terminal device 40, a paper transportation unit110, a print unit 120, a cutting unit 130, a drive unit 140 for drivingthe paper transportation unit 110, print unit 120, and cutting unit 130,and a control unit 200 for controlling internal printer 50 operations.

As shown in FIG. 2, the control unit 200 has memory (RAM 230) forstoring image data that is added to receipts and settings (see FIG. 3)relating to the image data, and based on these settings controls thereceipt design process for adding logos to the receipts by insertingimage data to the transaction information print data as furtherdescribed below. The RAM 230 could be composed of a plurality ofdifferent memory elements physically separated according to function orapplication. The data communication unit 100 handles sending data to andreceiving data from the image registration device 10.

The image registration device 10 is the host computer to which theprinter 50 is connected, and runs a printing control program 24 forediting the image data added to the receipt R, registering image data inthe printer 50, setting and getting parameter settings controlling thereceipt design process, and testing printing using the printer 50. Theuser controls setting the parameters of the receipt design process ofthe printer 50 and test printing by means of the display 13 and inputmeans such as a mouse 12 and keyboard 11. The image registration device10 and printer 50 are connected through a wireless or wired interface.The image registration device 10 is connected to the printer 50 duringimage data editing and registration, when setting and getting theparameters of the receipt design process, and during test printing, anddoes not need to be always connected to the printer 50.

The control arrangement of the image registration device 10 and printer50 is described next with reference to FIG. 2.

As shown in FIG. 2, the image registration device 10 comprises aninterface 21 for exchanging data with the printer 50, a CPU 25, ROM 26,RAM 27, keyboard 11, mouse 12, display 13, and hard disk drive 22connected to each other over a system bus 28.

In addition to the operating system (OS) and the printing controlprogram 24 for test printing and configuring the printer 50, the harddisk drive 22 stores other application programs, configuration settingsfor the printing control program 24 and application programs, and aconfiguration file related to the startup display. The OS 23 is thebasic software controlling the handling of input from the mouse 12 andkeyboard 11, displaying data on the display 13, and running applicationprograms.

The CPU 25 runs the OS 23 and printing control program 24, operationsbased on the application programs, and controls the image registrationdevice 10. The ROM 26 stores the BIOS, the basic program controllingsuch devices as the keyboard 11, display 13, and hard disk drive 22. TheOS 23 controls these devices by passing commands to the BIOS. RAM 27 isused by the CPU 25 as working memory for running application programsand the OS 23 read into RAM from the hard disk drive 22 or other storagemedium (including such optical media as CD-ROM and CD-R discs).

The printer 50 has an interface 51 for data communication with the POSterminal device 40 and image registration device 10, a papertransportation unit 110 with a receipt transportation motor 111 forconveying receipts R, and a print unit 120 with a print head 121 forprinting receipts synchronized to receipt R transportation. The printer50 also has a cutting unit 130, a drive unit 140, and a control unit 200for controlling internal printer 50 operations. The cutting unit 130 hasa receipt cutter 132 and a cutter motor 131 for driving the receiptcutter 132 to sever the printed receipt R from the roll paper. The driveunit 140 has a paper feed motor driver 141, head driver 142, and cuttermotor driver 143, and drives the motors and heads.

The control unit 200 comprises CPU 210, ROM 220, RAM 230, and an I/O(input/output) controller 240 interconnected via system bus 250. ROM 220has a control program block 221 for storing a control program that isrun by the CPU 210 to control printing and the receipt design process,and a control data block 222 for storing control data and tables usedfor printing and the receipt design process.

RAM 230 includes a working area block 231 used for storing flags andother data, a receive buffer 232, print buffer 233, and image data block234. The receive buffer 232 temporarily stores print data received bythe data communication unit 100 (see FIG. 1). The print buffer 233stores print data after conversion to a format enabling printing by theprint unit 120. The image data block 234 stores the image data that isprinted as a logo at a desired position on the receipt R.

RAM 230 also includes a top logo block 235 for storing parametersrelated to the top logo TL, that is, the image data added to the top ofthe receipt R; a bottom logo block 236 for storing parameters related tothe bottom logo BL, that is, the image data added to the bottom of thereceipt R; a watermark block 237 for storing parameters related to thewatermark WM printed on the receipt R; and a keyword logo block 238 forstoring parameters related to the keyword logo KL, that is, image datathat is added to the receipt R when triggered by a specific string ofdata. Based on these parameters, the CPU 210 processes and converts theprint data received from the image registration device 10. The contentof RAM 230 is also backed up in nonvolatile storage such as NVRAM sothat the content will not be lost when the power turns off. The imagedata block 234, top logo block 235, bottom logo block 236, watermarkblock 237, and keyword logo block 238 could also be rendered innonvolatile memory.

A logic circuit for complementing the functionality of the CPU 210 andhandling interface signals to peripheral circuits is also rendered inthe I/O controller 240 by means of gate arrays or a custom IC device,for example. The I/O controller 240 thus processes and then passes ordirectly passes print data and control data received from the POSterminal device 40 and image registration device 10 to the system bus250, and in conjunction with the CPU 210 processes and then passes ordirectly passes data and control signals output from the CPU 210 to thesystem bus 250 to the print unit 120 and other function units.

Thus arranged, the CPU 210 receives input signals and data from theoperating units of the printer 50 through the I/O controller 240according to the control program stored in ROM 220. Based on these inputsignals and data, the CPU 210 processes data in RAM 230 and then outputssignals and data through I/O controller 240 to the function units of theprinter 50 in order to control the printing process. An imageregistration unit 212 for registering and deleting images stored in apredetermined area of RAM 230 by running a control program is alsorendered in CPU 210.

The receipt design function of the printer 50 is described next. Theparameters related to processing image data in the receipt designprocess are described first below with reference to the parameterscolumn of the table shown in FIG. 3.

The parameter settings stored in the top logo block 235 include the keycode (referred to below as the ID) identifying the image data printed asthe top logo TL, the positioning of top logo TL position (align left,center, align right), and the number of lines to delete. This number oflines to delete is set in order to delete the unnecessary part of thereceived transaction information print data so that the top logo TL doesnot overlap that portion of the received transaction information printdata in the printed receipt, and denotes the number of lines to bedeleted starting from the first line of the received transactioninformation print data.

The parameters stored in the bottom logo block 236 include the key code(referred to below as the ID) identifying the image data printed as thebottom logo BL, and the positioning of the bottom logo.

The parameters stored in the watermark block 237 include the key code(referred to below as the ID) identifying the image data printed as thewatermark WM, the top margin L1 specifying the length from the top edgeof the receipt to the printing position of the first watermark, theprinting interval L2 defining the distance between watermarks, and thepositioning of the watermark.

The parameters stored in the keyword logo block 238 include the key code(referred to below as the ID) identifying the image data printed as thekeyword logo KL, the particular string of characters (referred to as thekey code) that triggers printing the keyword logo KL, the printingposition, and the number of lines to delete. When the character stringdefined as the key code is detected in the received transactioninformation print data, the keyword logo KL is printed based on theposition of the character string in the print data. The number of linesto delete is defined for the same reason as the number of lines todelete is defined in the top logo TL parameters, and specifies thenumber of lines to delete starting from the first print line after theline on which the character string is detected. The printing positiondeclared in the keyword logo KL parameters determines whether thekeyword logo KL is printed instead of the detected character string, isinserted to the line following the character string, or is inserted tothe line before the character string.

Examples of specific parameter values are shown in the lower part ofFIG. 3.

FIG. 4 shows a sample of a receipt R resulting from applying the receiptdesign process based on the parameter values shown in FIG. 3. The imagedata with an ID (key code) of 2020 is set as the top logo TL, which isprinted in the center at the top of the receipt R. Because the number oflines to delete is set to 3 for the top logo TL, the first three linesof transaction information print data starting from line 1 are deletedand not printed. Likewise, the image data with an ID (key code) of 2021is set as the bottom logo BL and printed in the center at the end of thereceipt R.

The image data identified by an ID (key code) of 2025 is set as thekeyword logo KL, which is printed centered on the next line after theline in which the character string (“strawberry”) defined as the keywordis detected (line 9 in this example). Furthermore, because the number oflines to delete for the keyword logo KL (the number of lines to deletefor the keyword “strawberry” as further described below) is set to 0 inthis example, the transaction information print data following the linecontaining the character string is printed and not deleted.

The image data with an ID (key code) of 2022 is set as the watermark WM,which is printed centered to the receipt R. The first watermark WM siprinted starting 40 dots from the top of the receipt R, and the intervalbetween watermarks WM is 20 dots as shown in FIG. 3 in this example.Note that while the top margin L1 and printing interval L2 are definedas the number of dots in this embodiment of the invention, the inventionis not so limited, and inches, millimeters, or other unit can be usedinstead.

Registering the image data and setting the parameter values used in thereceipt design process are described next. These processes arecontrolled by the printing control program 24 stored in the imageregistration device 10.

FIG. 5 is a block diagram showing the printing control program 24.

As shown in FIG. 5, this printing control program 24 comprises threeapplications: a gateway 60 for connecting to the printer 50, a graphicsregister 70 for registering image data in the printer 50, and a receiptdesigner 80 for setting the parameter values applied to the imagesregistered in the printer 50.

FIG. 6 shows an example of the gateway 60 application window.

The gateway 60 is an application for opening a connection to the printer50 so that the graphics register 70 and receipt designer 80 cancommunicate with the printer 50. As shown in FIG. 6, the gateway 60 hasa graphical user interface with a window presenting a connection nameselection box 61 for saving and selecting printer connection names, acommunication parameter box 62, and a tool selection box 63 for startingthe graphics register 70 and receipt designer 80. The communicationparameter box 62 enables setting the printer type, port type, port name,transfer rate, parity, stop bit, flow control, and bit length parametersfor the printer corresponding to the connection name selected in theconnection name selection box 61.

In order to register image data in the printer 50 or set the imagehandling parameters using the graphics register 70 or receipt designer80, the user selects the target printer from the connection nameselection box 61, and then clicks either button 64 or button 65 in thetool selection box 63. This selects and calls either the graphicsregister 70 or receipt designer 80 depending on whether button 64 orbutton 65 was selected. The selected tool, graphics register 70 orreceipt designer 80, is thus activated with a communication connectionopen to the printer using the communication settings defined in thecommunication parameter box 62.

The graphics register 70 is an image registration application (program)with functions for registering image data in the printer 50. Thegraphics register 70 also uses a graphical user interface in thisembodiment of the invention. The user stores various settings and imagedata using the tools displayed in the graphics register 70 window.

FIG. 7 shows an example of a first screen 70 a displayed inside window70A of the graphics register 70.

As shown in FIG. 7, a work stage selection and display unit 71containing four buttons 71 a to 71 d visually indicating the work stagesuntil the image data (graphic) is registered in the printer is presentedat the top of the first screen 70 a. As the user clicks on the buttonsshown in the work stage selection and display unit 71 of the graphicsregister 70, the content presented below the work stage selection anddisplay unit 71 changes according to which button 71 a to 71 d wasoperated. Which button 71 a to 71 d is currently selected is denoted bya selection rectangle 71 e displayed so that it encloses the selectedbutton 71 a to 71 d. In the example shown in FIG. 7, the selectionrectangle 71 e indicates that button 71 a identified as “1” is selectedand first screen 70 a is thus displayed.

An available graphics list box 72 presenting a list of the image filesto be registered is provided in the middle of the first screen 70 ashown in FIG. 7. Below the available graphics list box 72 are a listopening unit 73 a for opening the list to be displayed in the list box72, and a list editing unit 73 b for adding graphics to the list,deleting graphics from the list, and editing a graphic selected from thedisplayed list. The user selects the source image file of the image datato be registered in the printer 50 from the first screen 70 a shown inFIG. 7. The source image file is an image file stored in a local storagedevice of the image registration device 10. If the image registrationdevice 10 is connected to another storage device over a network, imagefiles stored on a network device can also be selected and used.

FIG. 8 shows a second screen 70 b displayed in the graphics register 70window 70A.

In the second screen 70 b shown in FIG. 8, a color configuration unit 74a for selecting monochrome or color printing and setting the color usedfor color printing, a halftone configuration unit 74 b for setting thedither type and brightness, and a size definition unit 74 c for settingthe size of the printed image are rendered below the available graphicslist box 72. The user defines the parameters of the image conversionprocess for generating the image data that is sent to the printer 50based on the source image file in this second screen 70 b. The user alsodefines the type of image conversion process that is applied to each ofthe image files listed in the list box 72 using the settings in thesecond screen 70 b shown in FIG. 8.

FIG. 9 shows the third screen 70 c displayed in the graphics register 70window 70A.

As shown in FIG. 9, this third screen 70 c is presented when the button71 c labelled “3”, is selected in FIG. 7 or FIG. 8, and the contentdisplayed below the work stage selection and display unit 71 isdifferent from that displayed in the first screen 70 a and second screen70 b shown in FIG. 7 and FIG. 8.

The area below the work stage selection and display unit 71 in thescreen 70 c shown in FIG. 9 includes a list box 75 identical to the listbox 72 shown in FIG. 7 and FIG. 8, and a registered graphics list box 76displaying a list of the image data that is actually stored in theprinter 50. Below these lists are a registered size display unit 77 afor displaying information about the size of a selected image when it isregistered in the printer 50, a key code input unit 77 b for setting thekey code of an image, and an image data registration unit 77 c forsending image data to, registering image data in, and deleting imagedata from the printer 50.

The user assigns the key code to the image data to be registered in theprinter 50 using the screen shown in FIG. 9, and then clicks theRegister button in the image data registration unit 77 c to generate theimage data to be registered in the printer 50 from the source image filebased on the defined parameters and then send the converted image datato the printer 50. The image registration unit 212 of the printer 50then writes the received image data in the printer 50 to RAM 230together with the assigned key code. This operation of saving an imagetogether with the assigned key code is referred to herein as“registering” the image.

In order to register an image in the printer 50, the graphics register70 first gets the unique serial number (printer ID number) of theprinter 50 from the printer 50. The graphics register 70 then recordsthe location of the source image file from which the image data to beregistered in the printer 50 is generated (that is, the logic pathdescribing where the source image file is stored starting from the rootdirectory), the key code, and the type and content (the number ofcolors, color reduction method, brightness, size, and bottom margin, forexample) of the image conversion process applied to the image file in aregistered image data information file (also referred to as a“registration log file”) 66. The image registration device 10 may beconnected to a plurality of printers, and a separate registration logfile is therefore generated for each printer. The file name of theregistered image data information file is therefore made unique to eachprinter by, for example, combining the printer name with the uniqueserial number.

This simple arrangement enables the graphics register 70 to know whatimage files are registered in a particular printer 50 and what type ofimage data was actually sent to the printer 50 by simply getting the keycodes stored in the printer 50. The image data registered in the printer50 is displayed in the registered graphics list box 76.

FIG. 10 shows a fourth screen 70d presented in the graphics register 70window 70A.

As shown in FIG. 10, this fourth screen 70 d is presented when thebutton 71 d labelled “4” is selected in FIG. 7, FIG. 8, or FIG. 9, andthe content displayed below the work stage selection and display unit 71is different from that displayed in the screens 70 a, 70 b, and 70 cshown in FIG. 7, FIG. 8 and FIG. 9, respectively.

The area below the work stage selection and display unit 71 in thescreen 70 d shown in FIG. 10 includes a registered graphics list box 77identical to the registered graphics list box 76 shown in FIG. 9. Belowthis registered graphics list box 77 are a registered informationacquisition unit 78 a for getting information about the image dataregistered in the printer 50, an options unit 78 b for defining optionalsettings, and a printing control unit 78 c for printing image data thatis registered in the printer 50.

When the user clicks on the GET INFO button in the registeredinformation acquisition unit 78 a, the graphics register 70 queries theprinter 50 to get only the key codes for the image data registered inthe printer 50. The graphics register 70 then uses these key codes toread the registered image data information file 66 and display the nameof the source image file, the key code, and the size of the registeredimage data in the registered graphics list box 77. The user can then usethe options unit 78 b to set the desired options, and use the printingcontrol unit 78 c to tell the printer 50 to print all of the imageslisted in the registered graphics list box 77 or just the selectedimages. To print a particular image, the graphics register 70 simplysends the key code with the print command to the printer 50.

By thus maintaining a registered image data information file 66 listingthe image data and corresponding key codes registered in the printer 50,the graphics register 70 can easily manage image data information basedon the key codes, can list the images registered in the printer 50 whenrequested by the user, and can tell the printer 50 to print any or allof the registered images.

The receipt designer 80 is described in detail next.

The receipt designer 80 is a parameter configuration application(parameter configuration means, parameter configuration program) withfunctions for configuring the images registered in the printer 50. Theseparameters include the printing position of the image data (top, bottomwatermark, and keyword logos), and details related to the printingposition. The user can thus control what image data is printed at whatposition by using the graphics register 70 to register image data in theprinter 50 and using the receipt designer 80 to define in detail wherethe image data will be printed on the receipt.

The receipt designer 80 also uses a graphical user interface. The userclicks on buttons to access different parameter settings. Note that thereceipt designer 80 has a window structure different from the graphicsregister 70, and the receipt designer 80 can also be started once thegraphics register 70 is running.

FIG. 11 shows a first screen 80 a that is presented in the main window80A of the receipt designer 80.

As shown in FIG. 11, a work stage selection and display unit 81containing six buttons 81 a to 81 f visually indicating the work stagesrequired to configure the image data (graphics) is presented at the topof the first screen 80 a. As the user clicks on the buttons shown in thework stage selection and display unit 81 of the receipt designer 80, thecontent presented below the work stage selection and display unit 81changes according to which button 81 a to 81 f was clicked. Which button81 a to 81 f is currently selected is denoted by a selection rectangle81 g displayed so that it encloses the selected button 81 a to 81 f. Inthe example shown in FIG. 11, the selection rectangle 81 g indicatesthat button 81 a identified as “1” is selected and first screen 80 a isthus displayed.

A registered graphics list box 82 presenting a list of the image filesregistered in the printer 50 is provided in the middle of the firstscreen 80 a shown in FIG. 11. Below the registered graphics list box 82is registered information acquisition unit 83 a for getting a list ofregistered graphics from the printer, and an options unit 83 b forimporting settings from an external file.

When the user clicks on the GET INFO button in the registeredinformation acquisition unit 83 a, the receipt designer 80 queries theprinter 50 to get the printer serial number, the key codes of imagesregistered in the printer, and the parameter settings for the registeredimages, and displays the information in the registered graphics list box82. The receipt designer 80 then uses these key codes and the printername to find the corresponding registered image data information file66, and then reads the registered image data information file 66 todisplay the names of the source image files corresponding to the imagekey codes (IDs) in the registered graphics list box 82. The image datashown in the list in FIG. 11 includes images for which the parametershave not yet been set and the printing position and other details aretherefore not yet determined.

When the user uses the mouse to click on the file name of a particularimage in the registered graphics list box 82 in order to see a previewof a particular image registered in the printer 50, the receipt designer80 reads the registered image data information file 66 to apply the sameimage conversion process to the source image file and present a previewof the result on the screen.

FIG. 12 to FIG. 16 show a second screen 80 b, third screen 80 c, fourthscreen 80 d, fifth screen 80 e, and sixth screen 80 f presented in thereceipt designer 80 window 80A.

The second screen 80 b shown in FIG. 12 is described first.

When the button 81 b denoted “2” in the work stage selection and displayunit 81 is clicked, the content of the area below the registeredgraphics list box 82 in the first screen 80 a shown in FIG. 11 changesto the second screen 80 b shown in FIG. 12. The second screen 80 b shownin FIG. 12 is used to set an image listed in the registered graphicslist box 82 as the top logo or bottom logo. The user selects an imagefrom the list in registered graphics list box 82 and then clicks one ofthe buttons in the Set/Delete unit 84 a to set the selected image as thetop logo or bottom logo. Detailed print settings for the selected imageare set in the attribute unit 84 b. This saves the settings for theselected image in the receipt designer 80, but does not send thesettings to the printer 50.

The third screen 80 c shown in FIG. 13 is described next.

When the button 81 c denoted “3” in the work stage selection and displayunit 81 is clicked, the content of the area below the registeredgraphics list box 82 in the first screen 80 a shown in FIG. 11 changesto the third screen 80 c shown in FIG. 13. The third screen 80 c shownin FIG. 13 is used to set an image listed in the registered graphicslist box 82 as the watermark. The user selects an image from the list inregistered graphics list box 82 and then clicks the button in theSet/Delete unit 85 a to set the selected image as the watermark.Detailed print settings for the selected image are set in the attributeunit 85 b. This saves the settings for the selected image in the receiptdesigner 80, but does not send the settings to the printer 50.

The fourth screen 80 d shown in FIG. 14 is described next.

When the button 81 d denoted “4” in the work stage selection and displayunit 81 is clicked, the content of the area below the registeredgraphics list box 82 in the first screen 80 a shown in FIG. 11 changesto the fourth screen 80 d shown in FIG. 14. The fourth screen 80 d shownin FIG. 14 is used to set an image listed in the registered graphicslist box 82 as a keyword logo. The user selects an image from the listin registered graphics list box 82, then enters the keyword in thekeyword input box 86 a, and then clicks the Add Keyword button in theAdd/Delete/Change unit 86 b to register the selected image as a keywordlogo. Detailed print settings for the selected image are set in theattribute unit 86 c. This saves the settings for the selected image inthe receipt designer 80, but does not send the settings to the printer50.

The fifth screen 80 e shown in FIG. 15 is described next.

When the button 81 e denoted “5” in the work stage selection and displayunit 81 is clicked, the content of the area below the registeredgraphics list box 82 in the first screen 80 a shown in FIG. 11 changesto the fifth screen 80 e shown in FIG. 15. The fifth screen 80 e shownin FIG. 15 is used for sending the image parameter settings to theprinter 50. When the user clicks the Save button in the registrationunit 87, the parameter settings saved by the receipt designer 80 areoutput to the printer 50 together with the key codes. When the key codesand settings are received by the printer 50, the image registration unit212 saves the key codes (IDs) and corresponding settings to the top logoblock 235, bottom logo block 236, watermark block 237, and keyword logoblock 238 appropriately. This completes setting the printing parametersfor the image data saved in the printer 50.

The receipt designer 80 can also save the settings output to the printerin a separate file. This file can be the registered image datainformation file generated by the graphics register 70, and the settingsfrom the receipt designer 80 can be appended to the registered imagedata information file.

The sixth screen 80 f shown in FIG. 16 is described next.

When the button 81 f denoted “6” in the work stage selection and displayunit 81 is clicked, the content of the area below the registeredgraphics list box 82 in the first screen 80 a shown in FIG. 11 changesto the sixth screen 80 f shown in FIG. 16. The sixth screen 80 f shownin FIG. 16 is used for getting, printing, and displaying settings fromthe printer 50. The user uses the registered information acquisitionunit 88 a to get the stored parameter settings from the printer 50, usesthe print settings unit 88 b to setup printing, and then uses the printunit 88 c to print. The image registration device 10 sends the printerinitialization command and a test print pattern to the printer 50 toprint.

By thus sending key codes and settings to the printer 50, the receiptdesigner 80 can thus define the printing position of the image dataregistered by the graphics register 70 together with detailed printsettings.

The interaction of the graphics register 70 and receipt designer 80 isdescribed next.

As described above, the graphics register 70 and receipt designer 80 donot acquire image data from the printer 50. The graphics register 70generates a registered image data information file 66 when the imagedata is registered, and thereafter the graphics register 70 and receiptdesigner 80 get only the serial number of the printer 50 and the keycodes of the registered image data from the printer 50. This registeredimage data information file can then be read to print and preview theimages corresponding to each key code.

Image data registration, deletion, and preview operations in thisembodiment of the invention are described next below with reference tothe accompanying flow charts, starting with the flow chart shown in FIG.17.

FIG. 17 is a flow chart of the process for registering image data in theprinter 50.

When the user uses the image data registration unit 77 c in the thirdscreen 70 c shown in FIG. 9 to input an image registration command tothe graphics register 70 (step S1), the graphics register 70 processesthe source image file based on the number of colors, color reductionmethod, brightness, size, and bottom margin settings defined for theimage data to generate the image data to be registered in the printer(step S2). The graphics register 70 then sends the resulting image datatogether with the key code to the printer 50 (step S3).

When the printer 50 receives the image data, the image registration unit212 saves the image data with the key code to the image data block 234,and thus registers the image data (step S7).

When sending image data to the printer 50 is finished, the graphicsregister 70 asks the printer 50 to return the serial number unique tothe printer 50 (step S4).

When the printer 50 receives a serial number request (step S8), theprinter 50 reads the serial number stored in a nonvolatile area of RAM230 (or ROM 220), and sends the serial number to the image registrationdevice 10, or more specifically the graphics register 70 (step S9).

When the graphics register 70 receives the serial number from theprinter 50 (step S5), the graphics register 70 saves the logic path tothe source image file from which the image data registered in theprinter 50 was generated, the key code, and the type and content of theimage conversion process applied to the image file (such as the numberof colors, color reduction method, brightness, size, and bottom margin)in the registered image data information file (registration log file)66. The file name for the registered image data information file 66 inthis embodiment of the invention is the printer name plus the printerserial number, and is thus unique to each printer.

As a result, when the graphics register 70 or receipt designer 80thereafter needs to reference the image file for registered image data,the graphics register 70 or receipt designer 80 can find thecorresponding registration log file using the printer name and printerserial number, and can thus confirm the content that was sent to theprinter without receiving the actual image data from the printer.

FIG. 18 is a flow chart of the process for deleting image data from theprinter 50.

When the user asserts an image deletion command to the graphics register70 using the image data registration unit 77 c in the third screen 70 cshown in FIG. 9 (step S11), the graphics register 70 sends a deletecommand specifying the key code of the image data to be deleted to theprinter 50 (step S12).

When the printer 50 receives this delete command (step S16), the imageregistration unit 212 deletes the image data corresponding to the keycode declared in the delete command from the image data block 234.

The graphics register 70 then asks the printer 50 to return the serialnumber unique to the printer 50 (step S13).

When the printer 50 receives the serial number request (step S17), theprinter 50 reads the serial number stored in a nonvolatile area of RAM230 (or ROM 220), and sends the serial number to the image registrationdevice 10, or more specifically the graphics register 70 (step S18).

When the graphics register 70 receives the serial number from theprinter 50 (step S14), the graphics register 70 locates the registrationlog file corresponding to the printer name and the serial numberreceived from the printer 50, and deletes the information (the key code,file path, number of colors, color reduction method, brightness, size,and bottom margin, for example) relating to the image data to be deletedfrom the corresponding registered image data information file (stepS15).

When image data is deleted from the printer 50 in this embodiment of theinvention, the corresponding information is also deleted from theregistered image data information file that is maintained by thegraphics register 70. As a result, the image data that is actuallystored in the printer 50 always matches the information about the imagedata registered in the printer 50 that is stored by the imageregistration device 10. It is therefore not necessary for the printer 50to send image data to the image registration device 10, and a systemthat is easy to use can be rendered even if the data transfer rate ofthe communication interface is slow.

FIG. 19 is a flow chart of the process for previewing image data that isregistered in the printer 50. In the operation described below thereceipt designer 80 is not communicating with the printer 50 andpresents a preview without receiving a key code from the printer 50.

When the user inputs a preview display command to the receipt designer80 (step S21), the receipt designer 80 instructs the printer 50 toreturn the key codes for the images registered in the printer (stepS22).

When the printer 50 receives the key code request (step S31), the imageregistration unit 212 reads and sends the list of key codes stored inthe image data block 234 of RAM 230 to the receipt designer 80 (stepS32).

When the receipt designer 80 receives the key code list from the printer50 (step S23), the receipt designer 80 requests the 500 to send theserial number unique to the printer 50 (step S24).

When the printer 50 receives the serial number request (step S33), theprinter 50 reads the serial number stored in a nonvolatile area of RAM230 (or ROM 220), and sends the serial number to the image registrationdevice 10, or more specifically the receipt designer 80 (step S34).

When the receipt designer 80 receives the serial number from the printer50 (step S25), the receipt designer 80 finds the registration log filecorresponding to the printer name and serial number received from theprinter, and opens the registered image data information file 66 (stepS26). The receipt designer 80 then reads the file path stored in theregistered image data information file 66 to locate the image data file(step S27), applies the same image conversion process using the numberof colors, color reduction method, brightness, size, and bottom marginparameters read from the registration log file, and presents a preview(step S28).

The receipt designer 80 in this embodiment of the invention can thusdisplay a preview of the image data by receiving only the image data keycode and printer serial number from the printer 50. Because the receiptdesigner 80 thus does not receive the image data from the printer 50,and a system that is easy to use can be rendered even if the datatransfer rate of the communication interface is slow.

This embodiment of the invention receives a serial number from theprinter 50 to maintain the integrity of the correlation between theregistered image data information files and printers when the imageregistration device 10 is connected to more than one printer andregisters image data in a plurality of printers. The invention is notlimited to using a serial number, however, and any value that uniquelyidentifies each printer can be used. The graphics register 70, forexample, could generate and store a specific code for each printer inthe printer, and use this generated code to identify each printer.

This embodiment of the invention is also described using the receiptdesigner 80 to present image previews. If the graphics register 70 isrendered with the same preview function, however, the graphics register70 can present a preview by executing the same steps described in FIG.19.

A separate registration log file is also stored for each printeridentification number in this embodiment of the invention, but if thecorrelation between the printer ID number and image registrationinformation (key code, file path, and image processing method) ismaintained, information for more than one printer can be maintained in asingle file, in a database, or in a registry, for example.

A printer, image registration method, and printer system according to afurther embodiment of the invention are described next below.

In the earlier embodiments of the invention described above, the imageregistration device 10 receives a unique printer serial number from theprinter 50 when registering image data in the printer 50, deleting imagedata from the printer 50, or previewing the image data in a printer 50,and uses this serial number to store image data linked to a key code inthe registered image data information file 66. With the arrangement andmethod of the first embodiment, however, problems can arise when notusing the graphics register 70 or receipt designer 80 that understandthis relationship between key codes and image data. For example, if adifferent computer overwrites the image data in the printer 50, or theimage registration device 10 uses an image registration device otherthan the graphics register 70 or receipt designer 80 to write image datain the printer 50, the correlation between the key codes and image dataknown to the graphics register 70 and receipt designer 80 from theregistered image data information file 66 may be broken, and the imageregistration device may associate the wrong image data with a particularkey code.

This further embodiment of the invention therefore relates to a printer,an image registration device, and a printer system arranged to preventsuch a mistaken image data correlation by the graphics register 70 andreceipt designer 80 when another computer or image registration deviceis also used. Note that functions that are basically the same asdescribed in the first embodiment are identified by like referencenumeral, and further description thereof is omitted below.

FIG. 20 is a control block diagram of an image registration device andprinter according to this second embodiment of the invention.

In addition to the elements of the earlier embodiments described above,this further embodiment of the invention additionally comprises a GUIDgeneration unit 211 (identification number overwriting unit), and a GUIDstorage unit 239 in RAM 230 for storing the generated GUID, as shown inFIG. 20.

The GUID that is a major component of this embodiment of the inventionis described below.

The printer 50 in this embodiment of the invention is arranged togenerate a unique identification number referred to as a GUID for usewhen registering image data, deleting image data, and previewing imagedata based on commands from a plurality of image registration devices.The GUID generation unit 211 shown in FIG. 20 generates this GUID whenthe image registration device 10 starts or ends an image dataregistration process (including deletion processes). The GUID isgenerated from the printer 50 serial number and a sequence number asdescribed below, for example. The sequence number preferably hassufficiently more digits than will be needed to accommodate the mostnumber of image data registration and deletion operations that mayactually be executed.

For example, if the printer 50 serial number is ABCDEFG, each new GUIDis generated by incrementing the sequence number as shown below.

GUID (initial value): ABCDEFG0000000000000000

-   -   (first iteration): ABCDEFG0000000000000001    -   (second iteration): ABCDEFG0000000000000002

After the guide reaches ABCDEFGFFFFFFFFFFFFFFFF, the next GUID revertsto ABCDEFG0000000000000000. While this GUID of ABCDEFG0000000000000000duplicates a previously used GUID, the first GUID of the same value willbe quite old if the number of digits in the sequence number issufficiently large, and will thus pose no practical problem.

This embodiment of the invention thus generates a new GUID based on theprinter 50 serial number each time an image data registration processruns. Because the GUID is based on the printer 50 serial number, theGUID is both unique to each printer and variable. Furthermore, becausethe GUID is generated each time an image data registration process runs,any particular printer 50 can be uniquely identified from every otherprinter.

A match between the GUID stored in the printer 50 and the GUID stored bya particular image registration device 10 means that a different imageregistration device has not modified the image data stored in theprinter 50 since the last time the particular image registration device10 registered (or deleted) image data in the printer 50. Likewise, amismatch between the GUID stored in the printer 50 and the GUID storedby a particular image registration device 10 means that a differentimage registration device modified the image data stored in the printer50 after the particular image registration device 10 last registered (ordeleted) image data in the printer 50.

If multiple image registration devices can register image data in aprinter, whether the image data information registered in a particularprinter 50 matches the image data information known to a particularimage registration device 10 can be determined by determining if theGUIDs are the same. This prevents deleting image data from the printerthat should not be deleted or previewing the wrong image data as aresult of a mismatch between the image data information stored in theprinter 50 and the image data that is understood by the imageregistration device 10 to be stored in the printer 50.

To enable this operation, the graphics register 70 first acquires theGUID from the printer 50 before registering image data in the printer50. After completing the image registration process, the printer 50generates a new GUID and the graphics register 70 acquires the new GUIDfrom the printer 50. The graphics register 70 then finds the registeredimage data information file identified by the old GUID, and records thelocation of the source image file from which the image data registeredin the printer 50 was generated (that is, the logic path describingwhere the source image file is stored starting from the root directory),the key code, and the type and content (the number of colors, colorreduction method, brightness, size, and bottom margin, for example) ofthe image conversion process applied to the image file in the registeredimage data information file (registration log file) 66. The new GUID isthen assigned to this registered image data information file 66. As aresult, the graphics register 70 maintains a correct correlation betweenthe GUID of the printer 50 and the corresponding registered image datainformation file 66.

To preview image data, the receipt designer 80 sends a command to theprinter 50 to acquire the key codes of the registered image data, theparameter settings for each image, and the current GUID from the printer50, and then lists this information in the registered graphics list box82. Based on the GUID of the printer 50, the receipt designer 80 locatesand reads the corresponding registered image data information file 66 tolist the file name corresponding to each image key code (ID) in theregistered graphics list box 82. If the GUID received from the printer50 does not match the GUID assigned in the registered image datainformation file 66, the receipt designer 80 knows that the image datain the printer 50 has been changed by some other device or means.

Interaction between the graphics register 70 and receipt designer 80 andthe printer 50 using the GUID is described next.

As described above, the graphics register 70 and receipt designer 80 donot acquire the image data from the printer 50. The graphics register 70generates a registered image data information file 66 when the imagedata is registered, and thereafter the graphics register 70 and receiptdesigner 80 get only the GUID of the printer 50 and the key codes of theregistered image data from the printer 50. The registered image datainformation file is then read to print and preview the imagescorresponding to each key code.

Image data registration, deletion, and preview operations in thisembodiment of the invention are described next below with reference tothe accompanying flow charts.

The process of registering image data in the printer 50 is describedfirst.

FIG. 21 is a flow chart of the process for registering image data in theprinter 50. The process whereby the graphics register 70 of the imageregistration device 10 registers image data in the printer 50 isdescribed below.

The graphics register 70 first asks the printer 50 to return the printerGUID (step S41).

When the printer 50 receives the GUID request, the printer 50 reads theGUID stored in the nonvolatile GUID storage unit 239 part (also referredto as NVRAM herein) of RAM 230, and sends the GUID to the imageregistration device 10, or more specifically the graphics register 70(step S42).

After receiving the GUID from the printer 50, the graphics register 70instructs the printer 50 to enter the NVRAM write mode (step S43). Theprinter 50 enters the NVRAM write mode when this command is received,and thus enables writing to the nonvolatile areas of RAM 230, that is,the image data block 234, top logo block 235, bottom logo block 236,watermark block 237, and keyword logo block 238 (step S44).

The graphics register 70 then processes the source image file based onthe number of colors, color reduction method, brightness, size, andbottom margin settings defined for the image data to generate the imagedata to be registered in the printer, and sends the registrationinformation, specifically the resulting image data and key code, to theprinter 50 (step S45).

When the printer 50 receives the image data, it saves the image datawith the key code to the image data block 234, and thus registers theimage data (step S46).

When the graphics register 70 finishes sending the registrationinformation, the graphics register 70 instructs the printer 50 to exitthe NVRAM write mode (step S47). When the printer 50 receives thiscommand, the GUID generation unit 211 generates a new GUID and saves thenew GUID by overwriting the content of the GUID storage unit 239 (stepS48). The NVRAM write mode thus ends, and the printer 50 returns to thenormal standby mode (step S49).

When the printer 50 terminates the NVRAM write mode, the printer 50sends the new GUID to the graphics register 70 (step S50). When thegraphics register 70 receives the new GUID from the printer 50, thegraphics register 70 opens the registered image data information file 66with the file name corresponding to the GUID received in step S42 (stepS51). The graphics register 70 then finds the key codes in theregistered image data information file 66, and overwrites theinformation in the registered image data information file 66corresponding to the key code and image data sent to the printer 50(step S52). This results in the image data and key codes registered inthe printer 50 matching the image data and key codes stored in theregistered image data information file 66.

The graphics register 70 then changes the name of the registered imagedata information file 66 based on the name of the new GUID received fromthe printer 50 (step S53). The file name of the registered image datainformation file 66 is the same as the new GUID or is linked to the newGUID. This completes registering image data in the printer 50.

When the graphics register 70 registers image data in the printer 50,the printer 50 thus overwrites the stored GUID with a new GUID in thisembodiment of the invention. The graphics register 70 also changes thename of the registered image data information file 66 file based on thisnew GUID, and can thus reliably know if the information in the printer50 has been changed or not.

If the image registration device 10 then communicates with the printer50 and the graphics register 70 determines that the GUID received fromthe printer 50 matches the GUID assigned to the registered image datainformation file 66, the graphics register 70 knows that the informationin the printer 50 has not been changed by another image registrationdevice since the last time the image registration device 10 connected tothe printer 50. On the other hand, if the GUID received from the printer50 does not match the GUID assigned to the registered image datainformation file 66, the graphics register 70 knows that the informationin the printer 50 has been changed by another image registration device.

This embodiment of the invention thus prevents the graphics register 70from changing the image data stored in the printer 50 erroneously as aresult of a change in the correlation between the image data and keycodes known to the graphics register 70, and thus prevents creating amismatch between the key codes and registered image data.

If the relationship between the key codes and image data that is knownto the image registration device becomes broken, the graphics register70 can acquire the key codes and image data information from the printer50 and simply reconstruct the registered image data information file 66.This links the new GUID acquired from the printer 50 with the registeredimage data information file 66, and thus maintains the correctcorrelation between key codes and image data for subsequent processes.

Deleting image data from the printer 50 is described next.

FIG. 22 is a flow chart of the process for deleting image data from theprinter 50.

The graphics register 70 first asks the printer 50 to return the printerGUID (step S61).

When the printer 50 receives the GUID request, the printer 50 reads theGUID stored in the nonvolatile GUID storage unit 239 part of RAM 230,and sends the GUID to the graphics register 70 (image registrationdevice 10) (step S62).

After receiving the GUID from the printer 50, the graphics register 70instructs the printer 50 to enter the NVRAM write mode (step S63). Theprinter 50 enters the NVRAM write mode when this command is received,and thus enables writing to the nonvolatile areas of RAM 230, that is,the image data block 234, top logo block 235, bottom logo block 236,watermark block 237, and keyword logo block 238 (step S64).

The graphics register 70 then sends the key code of the image data to bedeleted to the printer 50 (step S65). The printer 50 then deletes theimage data corresponding to the key code when the key code is received(step S66).

When the graphics register 70 finishes sending the key codes of imagedata to be deleted, the graphics register 70 instructs the printer 50 toexit the NVRAM write mode (step S67). When the printer 50 receives thiscommand, the GUID generation unit 211 generates a new GUID and saves thenew GUID by overwriting the content of the GUID storage unit 239 (stepS68). The NVRAM write mode thus ends, and the printer 50 returns to thenormal standby mode (step S69).

When the printer 50 terminates the NVRAM write mode, the printer 50sends the new GUID to the graphics register 70 (step S70).

When the graphics register 70 receives the new GUID from the printer 50,the graphics register 70 opens the registered image data informationfile 66 with the file name corresponding to the GUID received in stepS62 (step S71). The graphics register 70 then finds the key codes in theregistered image data information file 66, and deletes the key code andinformation corresponding to the deleted image data from the registeredimage data information file 66 (step S72). This results in the imagedata and key codes registered in the printer 50 matching the image dataand key codes stored in the registered image data information file 66.

The graphics register 70 then changes the name of the registered imagedata information file 66 based on the name of the new GUID received fromthe printer 50 (step S73). The file name of the registered image datainformation file 66 is the same as the new GUID or is linked to the newGUID. This completes deleting image data from the printer 50.

When the graphics register 70 deletes image data in the printer 50, theprinter 50 thus overwrites the stored GUID with a new GUID in thisembodiment of the invention. The graphics register 70 also changes thename of the registered image data information file 66 file based on thisnew GUID, and can thus reliably know if the information in the printer50 has been changed or not.

The printer 50 in this embodiment of the invention thus changes the GUIDwhen image data is deleted. Furthermore, by changing the file name ofthe registered image data information file 66 based on the new GUID, thegraphics register 70 can reliably know whether information in theprinter 50 has been changed or not.

Similarly to the situation after image data is registered in theprinter, if the image registration device 10 then communicates with theprinter 50 and the graphics register 70 determines that the GUIDreceived from the printer 50 matches the GUID assigned to the registeredimage data information file 66, the graphics register 70 knows that theinformation in the printer 50 has not been changed by another imageregistration device since the last time the image registration device 10connected to the printer 50. On the other hand, if the GUID receivedfrom the printer 50 does not match the GUID assigned to the registeredimage data information file 66, the graphics register 70 knows that theinformation in the printer 50 has been changed by another imageregistration device.

This embodiment of the invention thus prevents the graphics register 70from changing the image data stored in the printer 50 erroneously as aresult of a change in the correlation between the image data and keycodes known to the graphics register 70, and thus prevents creating amismatch between the key codes and registered image data.

If the relationship between the key codes and image data that is knownto the image registration device becomes broken, the graphics register70 can acquire the key codes and image data information from the printer50 and simply reconstruct the registered image data information file 66.This links the new GUID acquired from the printer 50 with the registeredimage data information file 66, and thus maintains the correctcorrelation between key codes and image data for subsequent processes.

A process for acquiring information, particularly key codes, related tothe image data registered in the printer 50 from the printer 50 andviewing the corresponding image data is described next.

FIG. 23 is a flow chart of a process for acquiring key codes from theprinter 50 and then previewing the image data. The graphics register 70acquires the key codes from the printer 50 in the example describedbelow. Note that the information can also be acquired and previewed bythe receipt designer 80 running the same process described below.

The graphics register 70 first asks the printer 50 to return the printerGUID (step S81).

When the printer 50 receives the GUID request, the printer 50 reads theGUID stored in the nonvolatile GUID storage unit 239 part of RAM 230,and sends the GUID to the graphics register 70 (image registrationdevice 10) (step S82).

After receiving the GUID from the printer 50, the graphics register 70asks the printer 50 to send the key codes (step S83). When the printer50 receives the key code request, the printer 50 reads the key codesfrom RAM 230 and sends the key codes to the graphics register 70 (stepS84).

When the graphics register 70 receives the key codes from the printer50, the graphics register 70 opens the registered image data informationfile 66 with the file name corresponding to the GUID received in stepS82 (step S85). The graphics register 70 then searches the key codes inthe registered image data information file 66, and finds the recordmatching the received key code (step S86). Based on instructions fromthe user, the graphics register 70 then references the file pathrecorded in the registered image data information file 66 for the imagedata corresponding to the key code, and displays the image data (stepS87).

The graphics register 70 thus receives the GUID before receiving keycodes from the printer 50 in this embodiment of the invention, andreferences the registered image data information file 66 correspondingto the GUID to display image data. The image data is thus displayedafter first confirming that the image data information in the printer 50has not been changed by another image registration device.

This embodiment of the invention thus prevents the graphics register 70from changing the image data stored in the printer 50 erroneously as aresult of a change in the correlation between the image data and keycodes known to the graphics register 70, and thus prevents creating amismatch between the key codes and registered image data.

If the relationship between the key codes and image data that is knownto the image registration device becomes broken, the graphics register70 can acquire the key codes and image data information from the printer50 and simply reconstruct the registered image data information file 66.This links the new GUID acquired from the printer 50 with the registeredimage data information file 66, and thus maintains the correctcorrelation between key codes and image data for subsequent processes.

The GUID is generated by adding a sequence number to the printer serialnumber in this embodiment of the invention, but if the printer onlyreturns the serial number, the GUID is only the sequence number. In thiscase, the image registration device combines the printer serial numberwith the GUID. Yet further, because it is only necessary that one GUIDis not the same as another GUID, some other ID that uniquely identifieseach printer can be used instead of the printer serial number. A timecode can also be used instead of the sequence number.

The GUID is tied to an individual printer and each printer generates aunique GUID in this embodiment of the invention, but the GUID can bedefined for each unit of image data. In this case the GUID is generatedfrom the printer serial number, the sequence number, and informationrelated to the image key code (such as the image file name or the keycode itself).

The image data could also be divided into categories, and the printercould generate a GUID for each category. In this case the write mode isset and cancelled when working with a particular category.

Although the present invention has been described in connection with thepreferred embodiments thereof with reference to the accompanyingdrawings, it is to be noted that various changes and modifications willbe apparent to those skilled in the art. Such changes and modificationsare to be understood as included within the scope of the presentinvention as defined by the appended claims, unless they departtherefrom.

1. A printer system comprising an image registration device that communicates with a printer, said printer comprising a data communication unit for receiving commands and image data sent from the image registration device, and an image registration unit for registering and storing the received image data in a designated storage area, wherein: the image registration device sends image data and an image data registration command to the printer; the data communication unit sends a printer identification number to the image registration device when image data is registered; and the image registration device records the image data and the received printer identification number in a registration log file.
 2. The printer system according to claim 1, wherein the image registration device generates a key code identifying a particular source image file containing image data, sends the key code paired with the image data to the printer, and records the path describing the storage location of the source image file of the image data linked to the key code in the registration log file.
 3. The printer system according to claim 2, wherein the image registration device applies an image conversion process to the source image file to generate and send the converted image data to the printer, and records the path describing the storage location of the source image file linked to the parameters of the applied image conversion process in the registration log file.
 4. The printer system according to claim 3, wherein the image registration device sends a delete command denoting the image data to be deleted to the printer when deleting image data from the printer; the image registration unit of the printer deletes the image data specified in the delete command and returns the printer identification number to the image registration device; and the image registration device finds the registration log file corresponding to the printer identification number and deletes the record of the deleted image data stored in the registration log file.
 5. The printer system according to claim 1, wherein the image registration device reads the registration log file to present a preview of image data registered in the printer.
 6. The printer system according to claim 1, wherein the printer additionally comprises an identification number overwriting unit, wherein: said identification number overwriting unit generates a new printer identification number and overwrites the existing printer identification number each time a process is run by the image registration unit; the data communication unit of the printer sends the new printer identification number to the image registration device after processing by the image registration unit ends; and the image registration device records the new printer identification number linked to the transmitted image data in the registration log file.
 7. The printer system according to claim 6, wherein the image registration device receives a printer identification number from the printer before sending image data, and if there is a registration log file entry that matches the received printer identification number, receives a new printer identification number from the printer after sending the image data to the printer, and adds the image data linked to the new printer identification number to the registration log file.
 8. The printer system according to claim 6, wherein the image registration device receives a first printer identification number from the printer before sending image data, and if there is not a registration log file entry that matches the received first printer identification number, receives a second printer identification number from the printer after sending the image data to the printer, and generates a registration log file containing the sent image data linked with said second printer identification number.
 9. The printer system according to claim 6, wherein the image registration device receives the printer identification number from the printer before sending a delete command for image data registered in the printer, and deletes the image data information from the registration log file after sending the delete command to the printer if there is a registration log file whose printer identification number matches the received printer identification number.
 10. The printer system according to claim 6, wherein the image registration device receives the printer identification number from the printer before displaying image data registered in the printer, and displays said image data without acquiring it from the printer if there is a registration log file whose printer identification number matches the received printer identification number.
 11. The printer system according to claim 6, wherein for image data in the registration log file linked by printer identification number to corresponding image data in the image registration unit of the printer, the image registration device references the registration log file and displays the image data without acquiring image data from the printer.
 12. A printer that is enabled to communicate with an image registration device, the printer comprising: a data communication unit for receiving image data sent from the image registration device; and an image registration unit for registering the received image data in a designated storage area; wherein the data communication unit sends to the image registration device a printer identification number enabling the image registration device to link the image data with the printer to which the image data was sent.
 13. The printer according to claim 12, further comprising an identification number rewriting unit for overwriting the printer identification number with a new printer identification number each time a process is executed by the image registration unit; wherein the data communication unit sends the new printer identification number to the image registration device each time the identification number rewriting unit overwrites the printer identification number.
 14. The printer according to claim 13, wherein the printer identification number is composed of the serial number of the printer and a predetermined character string; and the identification number rewriting unit rewrites the printer identification number by overwriting the predetermined character string.
 15. An image registration method comprising steps of: sending image data to be registered to a printer; receiving from the printer a printer identification number that identifies the printer; and recording the transmitted image data and the received printer identification number in a registration log file.
 16. The image registration method according to claim 15, further comprising steps of: generating a key code identifying image data; and additionally registering the path to the storage location of the source image file of the image data linked to the key code in the registration log file.
 17. The image registration method according to claim 16, further comprising steps of: generating the image data to be registered by applying an image conversion process to the source image file; and additionally recording the path describing the storage location of the source image file linked to the parameters of the applied image conversion process in the registration log file.
 18. The image registration method according to claim 17, further comprising steps of: sending a delete command denoting image data to be deleted to the printer; receiving a printer identification number from the printer; and locating a registration log file based on the printer identification number and deleting the image data associated with said registration log file.
 19. An image registration method according to claim 15, further comprising a step of reading the registration log file to present a preview of corresponding image data registered in the printer.
 20. The image registration method according to claim 19, wherein the printer identification number is received from the printer to identify the registration log file to be referenced when presenting a preview. 